Method and device used for wireless communication utilizing control plane and user plane layers

ABSTRACT

The present disclosure method and device for wireless communications, comprising: operating a first data block set; and transmitting first charging information; a size of data in the first data block set is used to generate the first charging information, the first charging information comprises a first identity (ID) set, and the first ID set comprises a first ID and a second ID; the first ID is a link layer ID; the operating action is receiving, a destination ID field of a MAC header of a MAC PDU used to carry the first data block set comprises at least partial bits in a first ID, when a destination link layer ID list maintained by a node indicated by the second ID comprises the first ID. The present disclosure determines a receiver or a generator of a first data block set, which improves accuracy of charging and enriches charging types of services.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of Chinese PatentApplication CN202010686444.0, filed on Jul. 16, 2020, the fulldisclosure of which is incorporated herein by reference.

BACKGROUND Technical Field

The present disclosure relates to transmission methods and devices inwireless communication systems, and in particular to a method and devicefor reporting user information, ensuring data consistency and chargingin wireless communications.

Related Art

Application scenarios of future wireless communication systems arebecoming increasingly diversified, and different application scenarioshave different performance demands on systems. In order to meetdifferent performance requirements of various application scenarios, the3rd Generation Partner Project (3GPP) Radio Access Network (RAN) #72plenary decided to conduct the study of New Radio (NR), or what iscalled fifth Generation (5G). The work Item (WI) of NR was approved atthe 3GPP RAN #75 plenary to standardize the NR.

In communications, whether Long Term Evolution (LTE) or 5G NR involvesfeatures of accurate delivery of reliable information, optimized energyefficiency ratio, determination of information efficiency, flexibleresource allocation, scalable system structure, efficient non-accesslayer information processing, low service interruption and droppingrate, high security and privacy and support for low-power consumption,which are of great significance to the maintenance of normalcommunications between a base station and a UE, reasonable scheduling ofresources and balancing of system payload. Those features can be calledthe cornerstone of high throughout and are characterized in meetingcommunication requirements of various services, as well as improvingspectrum utilization and service quality, which are indispensable inenhanced Mobile BroadBand (eMBB), Ultra Reliable Low LatencyCommunications (URLLC) and enhanced Machine Type Communications (eMTC).Meanwhile, in the following communication modes, covering IndustrialInternet of Things (IIoT), Vehicular to X (V2X), Device to Devicecommunications, Unlicensed Spectrum communications, User communicationquality monitoring, network planning optimization, Non-TerritorialNetworks (NTN), Territorial Networks (TN), Dual connectivity system,radio resource management and multi-antenna codebook selection,primary-link or sidelink communications, safe near field communications,networks involving relays, signaling design, adjacent cell management,service management and beamforming, extensive requirements of thesefeatures exist. Transmission methods of information are divided intobroadcast and unicast, both of which are essential for 5G systems forthat they are very helpful to meet the above requirements.

With the increase of scenarios and complexity of systems, higherrequirements are raised for reducing interruption rate and time delay,enhancing reliability and system stability, increasing serviceflexibility and saving power. Meanwhile, compatibility between differentversions of different systems should be taken into account whendesigning the systems.

SUMMARY

In a variety of communication scenarios, such as in a UE-to-UEcommunication scenario where a relay exists between UEs, due to reasonsof the lack of management of a central node and distributed generationof UE information, some information cannot be acquired by the network,and a UE cannot acquire another UE's information, resulting in a seriesof problems in management, especially in charging. As a relay node, whenusing unicast communication to relay, there exist one or more unicastlinks between the relay node and other nodes. There may be a pluralityof nodes forwarded by the relay node, and different nodes may also havecommunication requirements on the relay node. When different linksappear at the same time, the relationships of these links need to bedealt with, these links may be links on physical layer, link layer orlayer 3. The charging involved in communications between UEs isdifferent from the usual charging in that the charging is based on thereporting of users; which services are owned by a relay node and whichservices are relayed to other UEs need to be distinguished clearly tothe relay node as well as to the network statistics, since this mayinvolve different statistics and charging requirements, and if thecharging information cannot be unified, the complexity of the networkprocessing may be increased. On the other hand, in communicationsbetween UEs, it is better that information reported by different nodescan be referred to each other for checking, which cannot be achieved bythe existing data statistics and the reporting methods. At the sametime, due to the reasons of privacy or security, the relay UE may not beable to acquire all information of the other UEs, which brings newdifficulties to the generation and reporting of charging information,especially when a link layer identity (ID) between UEs is updated.Therefore, a comprehensive solution is needed, which can not only ensurethe security and privacy, but also solve generation of charginginformation of various links, where the method needs to be of lowcomplexity and the charging information is easy to process.

To address the above problem, the present disclosure provides asolution.

It should be noted that if no conflict is incurred, embodiments in anynode in the present disclosure and the characteristics of theembodiments are also applicable to any other node, and vice versa. Andthe embodiments in the present disclosure and the characteristics in theembodiments can be arbitrarily combined if there is no conflict.

The present disclosure provides a method in a first node for wirelesscommunications, comprising:

operating a first data block set; and

transmitting first charging information;

herein, a size of data in the first data block set is used to generatethe first charging information, the first charging information comprisesa first ID set, and the first ID set comprises a first ID and a secondID; the first ID is a link layer ID; the operating action is receiving,a destination ID field of a MAC header of a MAC PDU used to carry thefirst data block set comprises at least partial bits in a first ID, whena destination link layer ID list maintained by a node indicated by thesecond ID comprises the first ID, the first ID identifies a receiver ofthe first data block set, and when a destination link layer ID listmaintained by a node indicated by the second ID does not comprise thefirst ID, the first ID does not indicate a receiver of the first datablock set; or, the operating action is transmitting, a source ID fieldof a MAC header of a MAC PDU used to carry the first data block setcomprises at least partial bits in a first ID, when a source link layerID list maintained by a node indicated by the second ID comprises thefirst ID, the first ID indicates a generator of the first data blockset, and when a source link layer ID list maintained by a node indicatedby the second ID does not comprise the first ID, the first ID does notindicate a generator of the first data block set.

In one embodiment, a problem to be solved in the present disclosureincludes: when UEs are in communications with each other, especiallyinvolving sidelink communications, users need to update their identitiesfrom time to time to ensure security, which could occur at any time,besides, the update of ID and transmission of data are independent, andthe ID update of each link is also independent. However, when reportingcharging information, since the network cannot acquire the latest users'identities, it may not exactly know the meaning of these new identitiesand which user these identities indicate; on the other hand, charginginformation reported by the relay node needs to indicate for which usersor application or device or bearer or flow it serves, so that thenetwork can charge correctly. The present disclosure indicates an ID ofa receiver or a generator for different operations through a first IDand a second ID, thus solving the above problems.

In one embodiment, advantages of the above method include: in manycases, since the relay node can use the first ID and the second ID toindicate, the reported charging information is very simple with lowcomplexity; on the other hand, when the charging information generatedin the present disclosure is analyzed together with charging informationreported by other related UEs, a unified flow or charging chain can beformed, which is conducive for the network to verify these informationwhile a transmission of a great deal of unnecessary information isavoided. On the other hand, it can also ensure that the reportedcharging information is still clear when the ID is updated due to theprivacy and other reasons.

In one embodiment, characteristics of the present disclosure include: aMAC is a Medium Access Control.

In one embodiment, characteristics of the present disclosure include: aPDU is a Protocol Data Unit.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving, the first charging information isgenerated for data reception; and when the operating action istransmitting, the first charging information is generated for datatransmission.

Specifically, according to one aspect of the present disclosure, thefirst charging information comprises first information, when the firstcharging information is generated for data reception, the firstinformation is used to indicate whether the first ID identifies areceiver of the first data block set; when the first charginginformation is generated for data transmission, the first information isused to indicate whether the first ID identifies a generator of thefirst data block set.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving and the first ID does not indicate areceiver of the first data block set, the second ID is used to indicatea receiver of the first data block set; when the operating action istransmitting and the first ID does not indicate a generator of the firstdata block set, the second ID is used to indicate a generator of thefirst data block set.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving, the second ID is an IP address of areceiver of the first data block set; when the operating action istransmitting, the second ID is an IP address of a generator of the firstdata block set.

Specifically, according to one aspect of the present disclosure, thesecond ID is a first application layer ID, and the first applicationlayer ID is an ID related to an application layer.

Specifically, according to one aspect of the present disclosure, thesecond ID is a first group ID, the first group ID identifies a firstgroup, and the first group comprises a receiver of a first data blockset and a generator of the first data block set.

Specifically, according to one aspect of the present disclosure, thesecond ID is a link layer ID.

Specifically, according to one aspect of the present disclosure, thesecond ID is a flow ID.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving, and the first ID does not indicate areceiver of the first data block set, or, when the operating action istransmitting, and the first ID does not indicate a generator of thefirst data block set, the first charging information only comprises anIP address other than an IP address of the first node.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving, and the first ID does not indicate areceiver of the first data block set, or, when the operating action istransmitting, and the first ID does not indicate a generator of thefirst data block set, the first charging information only comprises anapplication layer ID other than an application layer ID of the firstnode.

Specifically, according to one aspect of the present disclosure, whenthe operating action is receiving, and the first ID does not indicate areceiver of the first data block set, or, when the operating action istransmitting, and the first ID does not indicate a generator of thefirst data block set, the first charging information only comprises alink layer ID other than a link layer ID of the first node.

Specifically, according to one aspect of the present disclosure,comprising:

when the first node has an IP address allocation function, the firsttransmitter transmits first information, and the first messageconfigures an IP address of a transmitter of the first data block set;when the first node does not have an IP address allocation function, thefirst receiver receives a second message, and the second messageindicates an IP address of a transmitter of the first data block set.

Specifically, according to one aspect of the present disclosure, an IPaddress of the first node and an IP address of a transmitter of thefirst data block set are at least the same in partial bits.

Specifically, according to one aspect of the present disclosure,comprising:

the first transmitter, transmitting a fourth message, the fourth messagecomprising at least one ID in the first ID set.

Specifically, according to one aspect of the present disclosure,comprising:

the first receiver, receiving a third message, the third message beingused to configure the first charging information, the third messagebeing used to indicate a first collection period, the first data blockset being operated within the first collection period, and the firsttransmitter, generating the first charging information for the firstcollection period.

Specifically, according to one aspect of the present disclosure,comprising:

the first receiver, receiving a first charging feedback message, thefirst charging feedback message indicating received charginginformation.

Specifically, according to one aspect of the present disclosure,comprising:

the first transmitter, transmitting a fifth message, the fifth messagebeing used to synchronize collection periods of different nodes.

Specifically, according to one aspect of the present disclosure, thefirst node is a UE.

Specifically, according to one aspect of the present disclosure, thefirst node is an IoT terminal.

Specifically, according to one aspect of the present disclosure, thefirst node is a relay.

Specifically, according to one aspect of the present disclosure, thefirst node is a vehicle terminal.

Specifically, according to one aspect of the present disclosure, thefirst node is an aircraft.

The present disclosure provides a first node for wirelesscommunications, comprising:

a first receiver, operating a first data block set; and

a first transmitter, transmitting first charging information;

herein, a size of data in the first data block set is used to generatethe first charging information, the first charging information comprisesa first ID set, and the first ID set comprises a first ID and a secondID; the first ID is a link layer ID; the operating action is receiving,a destination ID field of a MAC header of a MAC PDU used to carry thefirst data block set comprises at least partial bits in a first ID, whena destination link layer ID list maintained by a node indicated by thesecond ID comprises the first ID, the first ID identifies a receiver ofthe first data block set, and when a destination link layer ID listmaintained by a node indicated by the second ID does not comprise thefirst ID, the first ID does not indicate a receiver of the first datablock set; or, the operating action is transmitting, a source ID fieldof a MAC header of a MAC PDU used to carry the first data block setcomprises at least partial bits in a first ID, when a source link layerID list maintained by a node indicated by the second ID comprises thefirst ID, the first ID indicates a generator of the first data blockset, and when a source link layer ID list maintained by a node indicatedby the second ID does not comprise the first ID, the first ID does notindicate a generator of the first data block set.

In one embodiment, the present disclosure has the following advantagesover conventional schemes:

the method proposed in the present disclosure, in the process of theupdate of user's identities, especially when the network cannot acquirethese updated identities and the relay node cannot acquire privacyinformation of other nodes, the generated charging information can stillcarry enough information to meet charging requirements of the corenetwork. The present disclosure determines a generator or a receiver ofdata through a first ID and a second ID, where these identities can becompared and associated with the charging information transmitted by thegenerator and the receiver respectively, and the network can accuratelyacquire related data statistics through comparison and association so asto perform charging.

In one embodiment, the present disclosure has the following advantagesover conventional schemes:

the method proposed in the present disclosure allows the charginginformation generated by the relay node to clearly indicate whether asize of received or transmitted data is for the relay node or isforwarded to other nodes and specifically to which nodes, and whether itis from other nodes or is ready to be transmitted to other nodes, whichare necessary for charging related to relay. However, the conventionalscheme cannot support the charging function of communications betweenUEs involving a relay.

In one embodiment, the present disclosure has the following advantagesover conventional schemes:

the method proposed in the present disclosure is suitable for bothreceiving and transmitting, which is a unified solution. In addition,charging information generated by the node has a unified format with thelargest possibility. The first ID and the second ID, in different cases,can indicate different nodes, which is conducive to increasing thescalability of the solution, so that a plurality of chains are supportedto transmit-receive and relay at the same time. Meanwhile, when thenetwork processes the charging information, it can quickly process thedata according to different situations, which is conducive to reducingthe complexity of network. This is not supported by the conventionalscheme.

BRIEF DESCRIPTION OF THE DRAWINGS

Other features, objects and advantages of the present disclosure willbecome more apparent from the detailed description of non-restrictiveembodiments taken in conjunction with the following drawings:

FIG. 1 illustrates a flowchart of operating a first data block set andtransmitting first charging information according to one embodiment ofthe present disclosure;

FIG. 2 illustrates a schematic diagram of a network architectureaccording to one embodiment of the present disclosure;

FIG. 3 illustrates a schematic diagram of a radio protocol architectureof a user plane and a control plane according to one embodiment of thepresent disclosure;

FIG. 4 illustrates a schematic diagram of a first node according to oneembodiment of the present disclosure;

FIG. 5 illustrates a flowchart of transmission according to oneembodiment of the present disclosure;

FIG. 6 illustrates a flowchart of transmission according to oneembodiment of the present disclosure;

FIG. 7 illustrates a flowchart of transmission according to oneembodiment of the present disclosure;

FIG. 8 illustrates a flowchart of transmission according to oneembodiment of the present disclosure;

FIG. 9 illustrates a schematic diagram of a MAC PDU according to oneembodiment of the present disclosure;

FIG. 10 illustrates a schematic diagram of a link layer ID listmaintained by a node indicated by a second ID according to oneembodiment of the present disclosure;

FIG. 11 illustrates a schematic diagram of a collection period accordingto one embodiment of the present disclosure;

FIG. 12 illustrates a schematic diagram of a size of data in a firstdata block set being used to generate first charging informationaccording to one embodiment of the present disclosure;

FIG. 13 illustrates a schematic diagram of a fifth message being used tosynchronize collection periods of different nodes according to oneembodiment of the present disclosure;

FIG. 14 illustrates a schematic diagram of a processing device in afirst node according to one embodiment of the present disclosure.

DESCRIPTION OF THE EMBODIMENTS

The technical scheme of the present disclosure is described below infurther details in conjunction with the drawings. It should be notedthat the embodiments of the present disclosure and the characteristicsof the embodiments may be arbitrarily combined if no conflict is caused.

Embodiment 1

Embodiment 1 illustrates a flowchart of operating a first data block setand transmitting first charging information according to one embodimentof the present disclosure, as shown in FIG. 1 . In FIG. 1 , each boxrepresents a step. Particularly, the sequential order of steps in theseboxes does not necessarily mean that the steps are chronologicallyarranged.

In Embodiment 1, a size of data in the first data block set is used togenerate the first charging information, the first charging informationcomprises a first ID set, and the first ID set comprises a first ID anda second ID; the first ID is a link layer ID; the operating action isreceiving, a destination ID field of a MAC header of a MAC PDU used tocarry the first data block set comprises at least partial bits in afirst ID, when a destination link layer ID list maintained by a nodeindicated by the second ID comprises the first ID, the first IDidentifies a receiver of the first data block set, and when adestination link layer ID list maintained by a node indicated by thesecond ID does not comprise the first ID, the first ID does not indicatea receiver of the first data block set; or, the operating action istransmitting, a source ID field of a MAC header of a MAC PDU used tocarry the first data block set comprises at least partial bits in afirst ID, when a source link layer ID list maintained by a nodeindicated by the second ID comprises the first ID, the first IDindicates a generator of the first data block set, and when a sourcelink layer ID list maintained by a node indicated by the second ID doesnot comprise the first ID, the first ID does not indicate a generator ofthe first data block set.

In one embodiment, the first node is a UE.

In one embodiment, the first node is a relay.

In one embodiment, the first node is a UE-UE relay.

In one embodiment, the first node is a UE-to-UE relay.

In one embodiment, the first data block set transmits or receivesthrough one-to-many communications.

In one embodiment, the first data block set transmits or receivesthrough one-to-one communications.

In one embodiment, the first data block set is received by the firstnode through one-to-many communications, and is transmitted by the firstnode through one-to-one communications.

In one embodiment, the first data block set is received by the firstnode through one-to-one communications, and is transmitted by the firstnode through one-to-many communications.

In one embodiment, the first data block set at least comprises one datablock.

In one embodiment, the data block comprises K bit(s), K being a positiveinteger.

In one embodiment, the data block comprises a PDU.

In one embodiment, the data block comprises an SDU.

In one embodiment, the first data block set is transmitted via a PC5.

In one embodiment, the first data block set is received via a PC5.

In one embodiment, the first data block set is transmitted or receivedvia a PC5.

In one embodiment, the first data block set comprises IP data.

In one embodiment, the first data block set comprises an IP packet.

In one embodiment, the first data block set comprises Non-IP data.

In one embodiment, the first data block set comprises Non-IP structuraldata.

In one embodiment, the first data block set comprises NAS data.

In one embodiment, the first data block set comprises PC5-S data.

In one embodiment, the first data block set comprises PC5-RRC data.

In one embodiment, the first data block set comprises a SDAP PDU.

In one embodiment, the first data block set comprises a PDCP PDU.

In one embodiment, the first data block set comprises an RLC PDU.

In one embodiment, the first data block set comprises a MAC PDU.

In one embodiment, the first data block set comprises physical-layerdata.

In one embodiment, the first charging information is used for charging.

In one embodiment, the first charging information comprises usageinformation.

In one embodiment, the first charging information comprises userinformation.

In one embodiment, the first charging information comprises a usageinformation report.

In one embodiment, the first charging information comprises a userinformation report.

In one embodiment, the first charging information comprises a deviceinformation report.

In one embodiment, the first charging information is only for relayeddata.

In one subembodiment of the above embodiment, the first data block setis data needed to be relayed or data is relayed or data will be relayed.

In one embodiment, the first charging information comprises aUSAGE_INFORMATION_REPORT_LIST.

In one embodiment, the first charging information is part of aUSAGE_INFORMATION_REPORT_LIST.

In one embodiment, the first charging information isUsageInformationReportList-Info in a USAGE_INFORMATION_REPORT_LIST.

In one embodiment, the first charging information is ausage-information-report in a USAGE_INFORMATION_REPORT_LIST.

In one embodiment, the first charging information comprisesTransmission-info in a USAGE_INFORMATION_REPORT_LIST.

In one embodiment, the first charging information comprisesReception-info in a USAGE_INFORMATION_REPORT_LIST.

In one embodiment, when the operating action is receiving, the firstcharging information is generated for data reception; and when theoperating action is transmitting, the first charging information isgenerated for data transmission.

In one embodiment, the phrase of “the first charging information isgenerated for data reception” includes the following meaning: a size ofdata comprised or counted by the first charging information onlycomprises a size of received data.

In one embodiment, the phrase of “the first charging information isgenerated for data reception” includes the following meaning: a size ofdata comprised or counted by the first charging information onlycomprises a size of data received when the operating action isreceiving.

In one embodiment, the phrase of “the first charging information isgenerated for data reception” includes the following meaning: a size ofdata comprised or counted by the first charging information onlycomprises a size of data received by the first node when the operatingaction is receiving.

In one embodiment, the phrase of “the first charging information isgenerated for data transmission” includes the following meaning: a sizeof data comprised or counted by the first charging information onlycomprises a size of received data.

In one embodiment, the phrase of “the first charging information isgenerated for data transmission” includes the following meaning: a sizeof data comprised or counted by the first charging information onlycomprises a size of data transmitted when the operating action istransmitting.

In one embodiment, the phrase of “the first charging information isgenerated for data transmission” includes the following meaning: a sizeof data comprised or counted by the first charging information onlycomprises a size of data transmitted by the first node when theoperating action is transmitting.

In one embodiment, the phrase of “the first charging information isgenerated for data reception” includes the following meaning: a size ofdata counted by the first charging information only comprises a size oftransmitted data.

In one embodiment, when the first charging information is generated fordata reception, the first charging information comprises informationother than Transmission-info.

In one embodiment, when the first charging information is generated fordata transmission, the first charging information only comprisesinformation other than Reception-info.

In one embodiment, when the first charging information is generated fordata reception, the first charging information only comprisesinformation related to received data.

In one embodiment, when the first charging information is generated fordata transmission, the first charging information only comprisesinformation related to transmitted data.

In one embodiment, the first node is in coverage, and the first charginginformation is transmitted; when the first node is out of coverage, thefirst charging information is generated first, then stored, andtransmitted after the first node enters into the coverage.

In one embodiment, the first charging information is transmitted via aPC3ch interface.

In one embodiment, the first ID set only comprises the first ID and thesecond ID.

In one embodiment, the first ID set comprises an ID other than the firstID and the second ID.

In one embodiment, the first data block set is carried by one or moreMAC PDUs.

In one embodiment, the first data block set is carried as a MAC SDU ofone or more MAC PDUs.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set is a DST field.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set is an SRC field.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set comprises 16 most significantbits in the first ID.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set comprises that a number of bitsin the first ID is configured.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set comprises 8 most significant bitsin the first ID.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set comprises that a number of bitsin the first ID is configured.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises at least partial bits in thefirst ID.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises 16 most significant bits inthe first ID.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises that a number of bits in thefirst ID is configured.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises at least partial bits in thefirst ID.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises 8 most significant bits inthe first ID.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises that a number of bits in thefirst ID is configured.

In one embodiment, the link layer ID comprises a Link layer identifier.

In one embodiment, the link layer ID comprises a Link layer identity.

In one embodiment, the link layer ID comprises a Link layer ID.

In one embodiment, the link layer ID comprises a Layer2 ID.

In one embodiment, the link layer ID comprises a Layer-2 ID.

In one embodiment, the link layer ID comprises a L2 ID.

In one embodiment, the first ID is a prose-UE-id.

In one embodiment, the first ID is an element in the first charginginformation.

In one embodiment, the second ID is an element in the first charginginformation.

In one embodiment, a size of data in the first data block set is anelement in the first charging information.

In one embodiment, a MAC PDU used to carry the first data block set istransmitted at a PC5 interface.

In one embodiment, a physical channel occupied by a MAC PDU used tocarry to the first data block set comprises a Physical sidelink sharedchannel (PSSCH).

In one embodiment, a logical channel occupied by a MAC PDU used to carryto the first data block set comprises a Sidelink control channel (SCCH).

In one embodiment, a logical channel occupied by a MAC PDU used to carryto the first data block set comprises a Sidelink traffic channel (STCH).

In one embodiment, the first charging information comprises firstinformation, when the first charging information is generated for datareception, the first information is used to indicate whether the firstID identifies a receiver of the first data block set; when the firstcharging information is generated for data transmission, the firstinformation is used to indicate whether the first ID identifies agenerator of the first data block set.

In one embodiment, the first data block set is transmitted through anSL-SCH.

In one embodiment, the first data block set is transmitted throughsidelink.

In one subembodiment of the embodiment, the first information is anindicator.

In one subembodiment of the embodiment, the first information is a flag.

In one subembodiment of the embodiment, the first information indicateswhether the first data block set needs to be relayed.

In one subembodiment of the embodiment, the first information indicateswhether the first data block set is relayed.

In one subembodiment of the embodiment, the first information indicateswhether the first node is relayed.

In one subembodiment of the embodiment, the first information indicateswhether the operating action is used for relaying.

In one subembodiment of the embodiment, the first information implicitlyindicates whether the first data block set is relayed, and when thefirst ID and the second ID are used to indicate different nodes, thefirst data block set is relayed; when the first ID and the second ID areused to indicate a same node, the first data block set is not relayed.

In one embodiment, when the operating action is receiving and the firstID does not indicate a receiver of the first data block set, the secondID is used to indicate a receiver of the first data block set; when theoperating action is transmitting and the first ID does not indicate agenerator of the first data block set, the second ID is used to indicatea generator of the first data block set.

In one embodiment, when the second ID is used to indicate a receiver ofthe first data block set, the second ID is an ID of a receiver of thefirst data block set.

In one embodiment, when the second ID is used to indicate a receiver ofthe first data block set, the second ID identifies a receiver of thefirst data block set.

In one embodiment, when the second ID is used to indicate a receiver ofthe first data block set, the second ID can uniquely determine areceiver of the first data block set.

In one embodiment, when the second ID is used to indicate a receiver ofthe first data block set, the second ID can uniquely determine areceiver of the first data block set within a certain range.

In one embodiment, when the second ID is used to indicate a generator ofthe first data block set, the second ID is an ID of a generator of thefirst data block set.

In one embodiment, when the second ID is used to indicate a generator ofthe first data block set, the second ID identifies a generator of thefirst data block set.

In one embodiment, when the second ID is used to indicate a generator ofthe first data block set, the second ID can uniquely determine agenerator of the first data block set.

In one embodiment, when the second ID is used to indicate a generator ofthe first data block set, the second ID can uniquely determine agenerator of the first data block set within a certain range.

In one embodiment, a receiver of the first data block set is a receiverof the first data after being relayed.

In one embodiment, a generator of the first data block set is atransmitter of the first data block before being relayed.

In one embodiment, when the operating action is receiving, the firstnode transmits a second MAC PDU set, the second MAC PDU set carries thefirst data block set, and a node indicated by a destination ID field ofa MAC PDU header comprised in the second MAC PDU set is a receiver of afirst data block set.

In one embodiment, when the operating action is transmitting, a MAC PDUset used to carry the first data block set is generated by a first MACPDU set, the first node receives the first MAC PDU set, the first MACPDU set carries the first data block set, and a node indicated by asource ID field of a MAC PDU header of the first MAC PDU is a generatorof the first data block set.

In one embodiment, when the operating action is receiving and the firstdata block set is data that needs to be relayed, the first ID is used toindicate the first node, a receiver of the first data block set is areceiver of the first data after being relayed, the receiver of thefirst data block set is a node other than the first node, and the secondID is used to indicate a receiver of the first data block set.

In one subembodiment of the embodiment, the first information indicatesdata when the first data block set needs to be relayed.

In one embodiment, when the operating action is transmitting and thefirst data block set is relayed data, the first ID is used to indicatethe first node, a generator of the first data block set is a transmitterof the first data before being relayed, the generator of the first datablock set is a node other than the first node, and the second ID is usedto indicate a receiver of the first data block set.

In one subembodiment of the embodiment, the first information indicatesdata when the first data block set is relayed.

In one embodiment, when the operating action is receiving, the second IDis an IP address of a receiver of the first data block set; when theoperating action is transmitting, the second ID is an IP address of agenerator of the first data block set.

In one subembodiment of the embodiment, the second ID indicates a nodeother than the first node.

In one subembodiment of the embodiment, when the operating action isreceiving, the IP address is a target-IP-address.

In one subembodiment of the embodiment, when the operating action istransmitting, the IP address is a source-IP-address.

In one embodiment, when the operating action is receiving and the firstdata block set is not data that needs to be relayed, the first ID isused to indicate the first node, and the first node is a receiver of thefirst data block set.

In one subembodiment of the embodiment, the second ID indicates thefirst node.

In one subembodiment of the embodiment, the first information indicatesdata when the first data block set needs to be relayed.

In one embodiment, when the operating action is transmitting and thefirst data block set is not relayed data, the first ID is used toindicate the first node, and the first node is a generator of the firstdata block set.

In one subembodiment of the embodiment, the second ID indicates thefirst node.

In one subembodiment of the embodiment, the first information indicatesdata when the first data block set is relayed.

In one embodiment, the second ID is a first application layer ID, andthe first application layer ID is an ID related to an application layer.

In one embodiment, the second ID comprises an application ID.

In one embodiment, the second ID comprises a Prose application ID.

In one embodiment, the second ID comprises an application layer ID.

In one embodiment, the second ID comprises an application layer user ID.

In one embodiment, the second ID comprises an application layer groupID.

In one embodiment, the second ID comprises an application user ID.

In one embodiment, the second ID comprises a ProSe Application Code.

In one embodiment, the second ID comprises a Prose application layer ID.

In one embodiment, the second ID comprises a User ID.

In one embodiment, the second ID comprises a Prose user ID.

In one embodiment, the second ID comprises user info.

In one embodiment, the second ID comprises a UE ID.

In one embodiment, the second ID comprises a UE-identity.

In one embodiment, the second ID is a first group ID, the first group IDidentifies a first group, and the first group comprises a receiver ofthe first data block set and a generator of the first data block set.

In one embodiment, a generator of the first data block set is a nodeother than the first node.

In one embodiment, a receiver of the first data block set is a nodeother than the first node.

In one embodiment, whether a generator of the first data block set isthe first node is related to whether the first data block set is datathat needs to be relayed.

In one embodiment, whether a receiver of the first data block set is thefirst node is related to whether the first data block set is data thatneeds to be relayed.

In one embodiment, the second ID being a first group ID is used toindicate that the first data block set is relayed data.

In one embodiment, the second ID being a first group ID is used toindicate that the first data block set is data that needs to be relayed.

In one embodiment, the first group ID is a link layer ID.

In one embodiment, the first group comprises the first node.

In one embodiment, the first group does not comprise the first node.

In one embodiment, a group ID and a non-group ID use different codingschemes or different value ranges.

In one embodiment, the second ID is a link layer ID.

In one embodiment, the second ID is a flow ID.

In one embodiment, a flow indicated by the second ID comprises a relayedflow.

In one embodiment, a flow indicated by the second ID comprises a flowthat is not relayed.

In one embodiment, the first charging information only comprises an IPaddress other than an IP address of the first node.

In one embodiment, the first charging information is for one ofreceiving or transmitting.

In one embodiment, when the first data block set is data that needs tobe relayed, the first charging information is generated for one ofreceiving or transmitting, and the first charging information onlycomprises an IP address other than an IP address of the first node.

In one embodiment, when the operating action is receiving and the firstID does not indicate a receiver of the first data block set, the firstcharging information only comprises an IP address other than an IPaddress of the first node.

In one embodiment, when the operating action is receiving and adestination link layer ID list maintained by a node indicated by thesecond ID does not comprise the first identity, the first charginginformation only comprises an IP address other than an IP address of thefirst node.

In one embodiment, when the operating action is transmitting and thefirst ID does not indicate a generation of the first data block set, thefirst charging information only comprises an IP address other than an IPaddress of the first node.

In one embodiment, when the operating action is receiving and a sourcelink layer ID list maintained by a node indicated by the second ID doesnot comprise the first ID, the first charging information only comprisesan IP address other than an IP address of the first node.

In one embodiment, the first charging information only comprises anapplication layer ID other than an application layer ID of the firstnode.

In one embodiment, when the first data block set is data that needs tobe relayed, the first charging information is generated for one ofreceiving or transmitting, and the first charging information onlycomprises an application layer ID other than an application layer ID ofthe first node.

In one embodiment, when the operating action is receiving and the firstID does not indicate a receiver of the first data block set, the firstcharging information only comprises an application layer ID other thanan application layer ID of the first node.

In one embodiment, when the operating action is receiving and adestination link layer ID list maintained by a node indicated by thesecond ID does not comprise the first ID, the first charging informationonly comprises an application layer ID other than an application layerID of the first node.

In one embodiment, when the operating action is transmitting and thefirst ID does not indicate a generator of the first data block set, thefirst charging information only comprises an application layer ID otherthan an application layer ID of the first node.

In one embodiment, when the operating action is transmitting and asource link layer ID list maintained by a node indicated by the secondID does not comprise the first ID, the first charging information onlycomprises an application layer ID other than an application layer ID ofthe first node.

In one embodiment, the first charging information only comprises a linklayer ID other than a link layer ID of the first node.

In one embodiment, when the first data block set is data that needs tobe relayed, the first charging information is generated for one ofreceiving or transmitting, and the first charging information onlycomprises a link layer ID other than a link layer ID of the first node.

In one embodiment, when the operating action is receiving and the firstID does not indicate a receiver of the first data block set, the firstcharging information only comprises a link layer ID other than a linklayer ID of the first node.

In one embodiment, when the operating action is receiving and adestination link layer ID list maintained by a node indicated by thesecond ID does not comprise the first ID, the first charging informationonly comprises a link layer ID other than a link layer ID of the firstnode.

In one embodiment, when the operating action is transmitting and thefirst ID does not indicate a generator of the first data block set, thefirst charging information only comprises a link layer ID other than alink layer ID of the first node.

In one embodiment, when the operating action is transmitting and asource link layer ID list maintained by a node indicated by the secondID does not comprise the first ID, the first charging information onlycomprises a link layer ID other than a link layer ID of the first node.

In one embodiment, the operating action implicitly indicates forwardingor relaying.

In one embodiment, when the operating action is transmitting, theoperating action indicates forwarding or relaying.

In one embodiment, the first charging information only comprises beinggenerated after being forwarded or relayed.

In one embodiment, the first charging information only comprises thatthe first data block set is generated after being forwarded or relayed.

In one embodiment, the first charging information is generated only forforwarding or relaying.

In one embodiment, the first charging information is generated only fortransmitting.

In one embodiment, the meaning of the transmitting behavior includesforwarding.

In one embodiment, the meaning of the transmitting behavior includesrelaying.

Embodiment 2

Embodiment 2 illustrates a schematic diagram of a network architectureaccording to one embodiment of the present disclosure, as shown in FIG.2 . FIG. 2 is a diagram illustrating a V2X communication architecture of5G NR, Long-Term Evolution (LTE), and Long-Term Evolution Advanced(LTE-A) systems. The 5G NR or LTE network architecture may be called a5G System/Evolved Packet System (5GS/EPS) 200 or other appropriateterms.

The V2X communication architecture in Embodiment 2 may comprise a UE201, a UE 241 in communication with UE 201, an NG-RAN 202, a 5G CoreNetwork/Evolved Packet Core (5GC/EPC) 210, a Home Subscriber Server(HSS)/Unified Data Management (UDM) 220, a ProSe feature 250 and a ProSeapplication server 230. The V2X communication architecture may beinterconnected with other access networks. For simple description, theentities/interfaces are not shown. As shown in FIG. 2 , the V2Xcommunication architecture provides packet switching services. Thoseskilled in the art will readily understand that various conceptspresented throughout the present disclosure can be extended to networksproviding circuit switching services. The NG-RAN 202 comprises an NRnode B (gNB) 203 and other gNBs 204. The gNB 203 provides UE201-oriented user plane and control plane protocol terminations. The gNB203 may be connected to other gNBs 204 via an Xn interface (for example,backhaul). The gNB 203 may be called a base station, a base transceiverstation, a radio base station, a radio transceiver, a transceiverfunction, a Base Service Set (BSS), an Extended Service Set (ESS), aTransmitter Receiver Point (TRP) or some other applicable terms. The gNB203 provides an access point of the 5GC/EPC 210 for the UE 201. Examplesof the UE 201 include cellular phones, smart phones, Session InitiationProtocol (SIP) phones, laptop computers, Personal Digital Assistant(PDA), satellite Radios, non-terrestrial base station communications,Satellite Mobile Communications, Global Positioning Systems (GPS),multimedia devices, video devices, digital audio players (for example,MP3 players), cameras, game consoles, unmanned aerial vehicles (UAV),aircrafts, narrow-band Internet of Things (IoT) devices, machine-typecommunication devices, land vehicles, automobiles, wearable devices, orany other similar functional devices. Those skilled in the art also cancall the UE 201 a mobile station, a subscriber station, a mobile unit, asubscriber unit, a wireless unit, a remote unit, a mobile device, awireless device, a radio communication device, a remote device, a mobilesubscriber station, an access terminal, a mobile terminal, a wirelessterminal, a remote terminal, a handset, a user proxy, a mobile client, aclient or some other appropriate terms. The gNB 203 is connected to the5GC/EPC 210 via an S1/NG interface. The 5GC/EPC 210 comprises a MobilityManagement Entity (MME)/Authentication Management Field (AMF)/SessionManagement Function (SMF) 211, other MMEs/AMFs/SMFs 214, a ServiceGateway (S-GW)/User Plane Function (UPF) 212 and a Packet Date NetworkGateway (P-GW)/UPF 213. The MME/AMF/SMF 211 is a control node forprocessing a signaling between the UE 201 and the 5GC/EPC 210.Generally, the MME/AMF/SMF 211 provides bearer and connectionmanagement. All user Internet Protocol (IP) packets are transmittedthrough the S-GW/UPF 212, the S-GW/UPF 212 is connected to the P-GW/UPF213. The P-GW provides UE IP address allocation and other functions. TheP-GW/UPF 213 is connected to the Internet Service 230. The InternetService 230 comprises IP services corresponding to operators,specifically including Internet, Intranet, IP Multimedia Subsystem (IMS)and Packet Switching Streaming Services (PSS). The ProSe feature 250refers to logical functions of network-related actions needed forProximity-based Service (ProSe), including Direct Provisioning Function(DPF), Direct Discovery Name Management Function and EPC-level DiscoveryProSe Function. The ProSe application server 230 is featured withfunctions like storing EPC ProSe user ID, and mapping between anapplication-layer user ID and an EPC ProSe user ID as well as allocatingProSe-restricted code-suffix pool.

In one embodiment, the UE 201 and the UE 241 are connected via a PC5Reference Point.

In one embodiment, the ProSe feature 250 is connected with the UE 201and the UE 241 respectively via a PC3 Reference Point.

In one embodiment, the ProSe feature 250 is connected with the ProSeapplication server 230 via a PC2 Reference Point.

In one embodiment, the ProSe application server 230 is connected withthe ProSe application of the UE 201 and the ProSe application of the UE241 respectively via a PC1 Reference Point.

In one embodiment, the first node in the present disclosure is the UE201.

In one embodiment, a wireless link between the UE 201 and the UE 241corresponds to a sidelink in the present disclosure.

In one embodiment, the UE 201 supports relay transmission.

Embodiment 3

Embodiment 3 illustrates a schematic diagram of an example of a radioprotocol architecture of a user plane and a control plane according toone embodiment of the present disclosure, as shown in FIG. 3 . FIG. 3 isa schematic diagram illustrating an embodiment of a radio protocolarchitecture of a user plane 350 and a control plane 300. In FIG. 3 ,the radio protocol architecture for a first node (UE, gNB or a satelliteor an aircraft in NTN) and a second node (gNB, UE or a satellite or anaircraft in NTN), or between two UEs is represented by three layers,which are a layer 1, a layer 2 and a layer 3, respectively. which are alayer 1, a layer 2 and a layer 3, respectively. The layer 1 (L1) is thelowest layer and performs signal processing functions of various PHYlayers. The L1 is called PHY 301 in the present disclosure. The layer 2(L2) 305 is above the PHY 301, and is in charge of a link between afirst node and a second node, as well as two UEs via the PHY 301. L2 305comprises a Medium Access Control (MAC) sublayer 302, a Radio LinkControl (RLC) sublayer 303 and a Packet Data Convergence Protocol (PDCP)sublayer 304. All the three sublayers terminate at the second node. ThePDCP sublayer 304 provides multiplexing among variable radio bearers andlogical channels. The PDCP sublayer 304 provides security by encryptinga packet and provides support for a first node handover between secondnodes. The RLC sublayer 303 provides segmentation and reassembling of ahigher-layer packet, retransmission of a lost packet, and reordering ofa data packet so as to compensate the disordered receiving caused byHARQ. The MAC sublayer 302 provides multiplexing between a logicalchannel and a transport channel. The MAC sublayer 302 is alsoresponsible for allocating between first nodes various radio resources(i.e., resource block) in a cell. The MAC sublayer 302 is also in chargeof HARQ operation. The Radio Resource Control (RRC) sublayer 306 inlayer 3 (L3) of the control plane 300 is responsible for acquiring radioresources (i.e., radio bearer) and configuring the lower layer with anRRC signaling between a second node and a first node, where a signalingprocessed by the RRC sublayer comprises a PC5-RRC. The PC5 SignalingProtocol (PC5-S) sublayer 307 is responsible for the processing ofsignaling protocol at PC5 interface. The radio protocol architecture ofthe user plane 350 comprises layer 1 (L1) and layer 2 (L2). In the userplane 350, the radio protocol architecture for the first node and thesecond node is almost the same as the corresponding layer and sublayerin the control plane 300 for physical layer 351, PDCP sublayer 354, RLCsublayer 353 and MAC sublayer 352 in L2 layer 355, but the PDCP sublayer354 also provides a header compression for a higher-layer packet so asto reduce a radio transmission overhead. The L2 layer 355 in the userplane 350 also includes Service Data Adaptation Protocol (SDAP) sublayer356, which is responsible for the mapping between QoS flow and DataRadio Bearer (DRB) to support the diversity of traffic. Although notdescribed in the figure, the first node may comprise several higherlayers above the L2 305. In addition, it also includes a network layer(e.g., IP layer) terminated at a P-GW of the network side and anapplication layer or non-access layer (NAS, Non-Access-Stratum)terminated at the other side of the connection (e.g., a peer UE, aserver, etc.).

In one embodiment, the radio protocol architecture in FIG. 3 isapplicable to the first node in the present disclosure.

In one embodiment, the radio protocol architecture in FIG. 3 isapplicable to a generator of the first data block set in the presentdisclosure.

In one embodiment, the radio protocol architecture in FIG. 3 isapplicable to a receiver of the first data block set in the presentdisclosure.

In one embodiment, the first data block set in the present disclosure isgenerated by a layer above the PHY301 or the MAC302 or the RLC303 or thePDCP304 or PC5-S307 or RRC306 or PHY351 or MAC352 or RLC353 or PDCP354or SDAP356 or SDAP356.

In one embodiment, the first message in the present disclosure isgenerated by the PC5-S307 or the RRC306 or the IP layer.

In one embodiment, the second message in the present disclosure isgenerated by the PC5-S307 or the RRC306 or the IP layer.

In one embodiment, the third message in the present disclosure isgenerated by the NAS layer.

In one embodiment, the fourth message in the present disclosure isgenerated by the NAS layer.

In one embodiment, the first charging feedback message in the presentdisclosure is generated by the NAS layer.

In one embodiment, the fifth message in the present disclosure isgenerated by the PC5-S layer 307 or the RRC306.

Embodiment 4

Embodiment 4 illustrates a schematic diagram of a first communicationdevice and a second communication device in the present disclosure, asshown in FIG. 4 . FIG. 4 is a block diagram of a first communicationdevice 450 in communication with a second communication device 410 in anaccess network.

The first communication device 450 comprises a controller/processor 459,a memory 460, a data source 467, a transmitting processor 468, areceiving processor 456, a multi-antenna transmitting processor 457, amulti-antenna receiving processor 458, a transmitter/receiver 454 and anantenna 452.

The second communication device 410 comprises a controller/processor475, a memory 476, a receiving processor 470, a transmitting processor416, a multi-antenna receiving processor 472, a multi-antennatransmitting processor 471, a transmitter/receiver 418 and an antenna420.

In a transmission from the second communication device 410 to the firstcommunication device 450, at the first communication device 410, ahigher layer packet from the core network is provided to acontroller/processor 475. The controller/processor 475 provides afunction of the L2 layer. In the transmission from the secondcommunication device 410 to the first communication device 450, thecontroller/processor 475 provides header compression, encryption, packetsegmentation and reordering, and multiplexing between a logical channeland a transport channel, and radio resources allocation for the firstcommunication device 450 based on various priorities. Thecontroller/processor 475 is also responsible for retransmission of alost packet and a signaling to the first communication device 450. Thetransmitting processor 416 and the multi-antenna transmitting processor471 perform various signal processing functions used for the L1 layer(that is, PHY). The transmitting processor 416 performs coding andinterleaving so as to ensure an FEC (Forward Error Correction) at thesecond communication device 410, and the mapping to signal clusterscorresponding to each modulation scheme (i.e., BPSK, QPSK, M-PSK, M-QAM,etc.). The multi-antenna transmitting processor 471 performs digitalspatial precoding, including codebook-based precoding andnon-codebook-based precoding, and beamforming on encoded and modulatedsymbols to generate one or more spatial streams. The transmittingprocessor 416 then maps each spatial stream into a subcarrier. Themapped symbols are multiplexed with a reference signal (i.e., pilotfrequency) in time domain and/or frequency domain, and then they areassembled through Inverse Fast Fourier Transform (IFFT) to generate aphysical channel carrying time-domain multi-carrier symbol streams.After that the multi-antenna transmitting processor 471 performstransmission analog precoding/beamforming on the time-domainmulti-carrier symbol streams. Each transmitter 418 converts a basebandmulticarrier symbol stream provided by the multi-antenna transmittingprocessor 471 into a radio frequency (RF) stream. Each radio frequencystream is later provided to different antennas 420.

In a transmission from the second communication device 410 to the firstcommunication device 450, at the second communication device 450, eachreceiver 454 receives a signal via a corresponding antenna 452. Eachreceiver 454 recovers information modulated to the RF carrier, convertsthe radio frequency stream into a baseband multicarrier symbol stream tobe provided to the receiving processor 456. The receiving processor 456and the multi-antenna receiving processor 458 perform signal processingfunctions of the L1 layer. The multi-antenna receiving processor 458performs receiving analog precoding/beamforming on a basebandmulticarrier symbol stream from the receiver 454. The receivingprocessor 456 converts the baseband multicarrier symbol stream afterreceiving the analog precoding/beamforming from time domain intofrequency domain using FFT. In frequency domain, a physical layer datasignal and a reference signal are de-multiplexed by the receivingprocessor 456, wherein the reference signal is used for channelestimation, while the data signal is subjected to multi-antennadetection in the multi-antenna receiving processor 458 to recover anythe first communication device-targeted spatial stream. Symbols on eachspatial stream are demodulated and recovered in the receiving processor456 to generate a soft decision. Then the receiving processor 456decodes and de-interleaves the soft decision to recover the higher-layerdata and control signal transmitted on the physical channel by thesecond communication node 410. Next, the higher-layer data and controlsignal are provided to the controller/processor 459. Thecontroller/processor 459 performs functions of the L2 layer. Thecontroller/processor 459 can be connected to a memory 460 that storesprogram code and data. The memory 460 can be called a computer readablemedium. In the transmission from the second communication device 410 tothe second communication device 450, the controller/processor 459provides demultiplexing between a transport channel and a logicalchannel, packet reassembling, decryption, header decompression andcontrol signal processing so as to recover a higher-layer packet fromthe core network. The higher-layer packet is later provided to allprotocol layers above the L2 layer, or various control signals can beprovided to the L3 layer for processing.

In a transmission from the first communication device 450 to the secondcommunication device 410, at the second communication device 450, thedata source 467 is configured to provide a higher-layer packet to thecontroller/processor 459. The data source 467 represents all protocollayers above the L2 layer. Similar to a transmitting function of thesecond communication device 410 described in the transmission from thesecond communication device 410 to the first communication device 450,the controller/processor 459 performs header compression, encryption,packet segmentation and reordering, and multiplexing between a logicalchannel and a transport channel based on radio resources allocation soas to provide the L2 layer functions used for the user plane and thecontrol plane. The controller/processor 459 is also responsible forretransmission of a lost packet, and a signaling to the secondcommunication device 410. The transmitting processor 468 performsmodulation mapping and channel coding. The multi-antenna transmittingprocessor 457 implements digital multi-antenna spatial precoding,including codebook-based precoding and non-codebook-based precoding, aswell as beamforming. Following that, the generated spatial streams aremodulated into multicarrier/single-carrier symbol streams by thetransmitting processor 468, and then modulated symbol streams aresubjected to analog precoding/beamforming in the multi-antennatransmitting processor 457 and provided from the transmitters 454 toeach antenna 452. Each transmitter 454 first converts a baseband symbolstream provided by the multi-antenna transmitting processor 457 into aradio frequency symbol stream, and then provides the radio frequencysymbol stream to the antenna 452.

In the transmission from the first communication device 450 to thesecond communication device 410, the function at the secondcommunication device 410 is similar to the receiving function at thefirst communication device 450 described in the transmission from thesecond communication device 410 to the first communication device 450.Each receiver 418 receives a radio frequency signal via a correspondingantenna 420, converts the received radio frequency signal into abaseband signal, and provides the baseband signal to the multi-antennareceiving processor 472 and the receiving processor 470. The receivingprocessor 470 and multi-antenna receiving processor 472 collectivelyprovide functions of the L1 layer. The controller/processor 475 providesfunctions of the L2 layer. The controller/processor 475 can be connectedwith the memory 476 that stores program code and data. The memory 476can be called a computer readable medium. In the transmission from thefirst communication device 450 to the second communication device 410,the controller/processor 475 provides de-multiplexing between atransport channel and a logical channel, packet reassembling,decryption, header decompression, control signal processing so as torecover a higher-layer packet from the UE 450. The higher-layer packetcoming from the controller/processor 475 may be provided to the corenetwork.

In one embodiment, the first communication device 450 comprises at leastone processor and at least one memory. The at least one memory comprisescomputer program codes; the at least one memory and the computer programcodes are configured to be used in collaboration with the at least oneprocessor, the first communication device 450 at least receives a firstMAC PDU, the first MAC PDU comprises a first MAC header and at least afirst MAC subPDU, the first MAC header comprises at least partial bitsof a first link layer ID and at least partial bits of a second linklayer ID; the first MAC subPDU comprises a first MAC sub-header and afirst MAC SDU, and the first MAC subPDU implicitly indicates a targetlink layer ID; when the target link layer ID belongs to a first ID set,transmits a second MAC PDU, the second MAC PDU comprises a second MACheader and at least a second MAC subPDU, the second MAC subPDU comprisesa second MAC sub-head, the second MAC subPDU comprises at least partialbits in the first MAC SDU, and the second MAC header comprises at leastpartial bits in the target link layer ID; when the target link layer IDis a second link layer ID, drops a transmission of a MAC PDU comprisingat least partial bits of the first MAC SDU; herein, the first ID setcomprises at least one link layer ID.

In one embodiment, the first communication device 450 comprises a memorythat stores a computer readable instruction program. The computerreadable instruction program generates an action when executed by atleast one processor. The action includes: receiving a first MAC PDU, thefirst MAC PDU comprising a first MAC header and at least first MACsubPDU, the first MAC header comprising at least partial bits of a firstlink layer ID and at least partial bits of a second link layer ID; thefirst MAC subPDU comprising a first MAC sub-header and a first MAC SDU,and the first MAC subPDU implicitly indicating a target link layer ID;when the target link layer ID belongs to a first ID set, transmitting asecond MAC PDU, the second MAC PDU comprising a second MAC header and atleast a second MAC subPDU, the second MAC subPDU comprising a second MACsub-head, the second MAC subPDU comprising at least partial bits in thefirst MAC SDU, and the second MAC header comprising at least partialbits in the target link layer ID; when the target link layer ID is asecond link layer ID, dropping a transmission of a MAC PDU comprising atleast partial bits of the first MAC SDU; herein, the first ID setcomprises at least one link layer ID.

In one embodiment, the second communication device 410 comprises atleast one processor and at least one memory. The at least one memorycomprises computer program codes; the at least one memory and thecomputer program codes are configured to be used in collaboration withthe at least one processor. The second communication device 410 at leasttransmits a first MAC PDU, the first MAC PDU comprises a first MACheader and at least first MAC subPDU, the first MAC header comprises atleast partial bits of a first link layer ID and at least partial bits ofa second link layer ID; the first MAC subPDU comprises a first MACsub-header and a first MAC SDU, and the first MAC subPDU implicitlyindicates a target link layer ID; when the target link layer ID belongsto a first ID set, a receiver of the first MAC PDU transmits a secondMAC PDU, the second MAC PDU comprises a second MAC header and at least asecond MAC subPDU, the second MAC subPDU comprises a second MACsub-head, the second MAC subPDU comprises at least partial bits in thefirst MAC SDU, and the second MAC header comprises at least partial bitsin the target link layer ID; when the target link layer ID is a secondlink layer ID, a receiver of the first MAC PDU drops a transmission of aMAC PDU comprising at least partial bits of the first MAC SDU; herein,the first ID set comprises at least one link layer ID.

In one embodiment, the second communication device 410 comprises amemory that stores a computer readable instruction program. The computerreadable instruction program generates an action when executed by atleast one processor. The action includes: transmitting a first MAC PDU,the first MAC PDU comprising a first MAC header and at least first MACsubPDU, the first MAC header comprising at least partial bits of a firstlink layer ID and at least partial bits of a second link layer ID; thefirst MAC subPDU comprising a first MAC sub-header and a first MAC SDU,and the first MAC subPDU implicitly indicating a target link layer ID;when the target link layer ID belongs to a first ID set, a receiver ofthe first MAC PDU transmitting a second MAC PDU, the second MAC PDUcomprising a second MAC header and at least a second MAC subPDU, thesecond MAC subPDU comprising a second MAC sub-head, the second MACsubPDU comprising at least partial bits in the first MAC SDU, and thesecond MAC header comprising at least partial bits in the target linklayer ID; when the target link layer ID is a second link layer ID, areceiver of the first MAC PDU dropping a transmission of a MAC PDUcomprising at least partial bits of the first MAC SDU; herein, the firstID set comprises at least one link layer ID.

In one embodiment, the first communication device 450 corresponds to afirst node in the present disclosure.

In one embodiment, the second communication device 410 corresponds to agenerator of a first data block set in the present disclosure.

In one embodiment, the second communication device 410 corresponds to areceiver of a first data block set in the present disclosure.

In one embodiment, the first communication device 450 is a UE.

In one embodiment, the first communication device 450 is a vehicleterminal.

In one embodiment, the second communication device 410 is a UE.

In one embodiment, the first communication device 410 is a vehicleterminal.

In one embodiment, the receiver 456 (including the antenna 460), thereceiving processor 452 and the controller/processor 490 are used toreceive the first data block set in the present disclosure.

In one embodiment, the transmitter 456 (including the antenna 460), thetransmitting processor 455 and the controller/processor 490 are used totransmit the first data block set in the present disclosure.

In one embodiment, the transmitter 456 (including the antenna 460), thetransmitting processor 455 and the controller/processor 490 are totransmit the fifth message in the present disclosure.

In one embodiment, the receiver 416 (including the antenna 420), thereceiving processor 412 and the controller/processor 440 are used toreceive the fifth message in the present disclosure.

Embodiment 5

Embodiment 5 illustrates a flowchart of radio signal transmissionaccording to one embodiment in the present disclosure, as shown in FIG.5 . In FIG. 5 , the U01 corresponds to a first node in the presentdisclosure, a 2a node U02 is a node in communications with the firstnode U01, a 3a node U03 is a core network node. It is particularlyunderlined that the order illustrated in the embodiment does not putconstraints over sequences of signal transmissions and implementationsand steps in F51 and F52 are optional.

The first node U01 receives a first data block set in step S5101;transmits a first message in step S5102; transmits a fourth message instep S5103; receives a third message in step S5104; transmits firstcharging information in step S5105; receives a first charging feedbackmessage in step S5106; and transmits a fifth message in step S5107.

The 2a node U02 transmits the first data block set in step S5201;receives the first message in step S5202; and receives the fifth messagein step S5203.

The 3a node U03 receives the fourth message in step S5301; transmits thethird message in step S5302; receives the first charging information instep S5303; and transmits the first charging feedback message in stepS5304.

In Embodiment 5, a size of data in the first data block set is used togenerate the first charging information, the first charging informationcomprises a first ID set, and the first ID set comprises a first ID anda second ID; the first ID is a link layer ID; a destination ID field ofa MAC header of a MAC PDU used to carry the first data block setcomprises at least partial bits in a first ID, when a destination linklayer ID list maintained by a node indicated by the second ID comprisesthe first ID, the first ID identifies a receiver of the first data blockset, and when a destination link layer ID list maintained by a nodeindicated by the second ID does not comprise the first ID, the first IDdoes not indicate a receiver of the first data block set.

In one embodiment, the first node U01 is a UE.

In one embodiment, the 2a node U02 is a UE.

In one embodiment, the 2a node U02 is a remote UE.

In one embodiment, a communication interface between the first node U01and the 2a node U02 is a PC5.

In one embodiment, a communication interface between the first node U01and the 2a node U02 is a Uu.

In one embodiment, the first node U01 forwards the first data block set.

In one embodiment, the first node U01 drops forwarding the first datablock set.

In one subembodiment of the above embodiment, the action of droppingforwarding includes, the first node U01 is assembled with the first datablock set.

In one subembodiment of the above embodiment, the action of droppingforwarding includes, handing over the first data block set to an higherlayer for processing.

In one subembodiment of the above embodiment, when using layer 2forwarding or relaying, the action of dropping forwarding includes,handing over the first data block set to a layer above layer 2 forprocessing.

In one subembodiment of the above embodiment, when using layer 3forwarding or relaying, the action of dropping forwarding includes,handing over the first data block set to an application layer forprocessing.

In one embodiment, the forwarding action includes relaying.

In one embodiment, an SRC field of a MAC PDU header carrying the firstdata block set identifies the 2a node U02; a DST field of a MAC PDUheader carrying the first data block set is used to identify the firstnode U01.

In one embodiment, an SRC field of a MAC PDU header carrying the firstdata block set identifies the 2a node U02; a DST field of a MAC PDUheader carrying the first data block set is used to identify a nodeother than the first node U01.

In one embodiment, when the first node U01 drops forwarding the firstdata block set, a destination link layer ID list maintained by a nodeindicated by the second ID comprises the first ID, and the first IDidentifies a receiver of the first data block set.

In one subembodiment of the above embodiment, the first ID identifiesthe first node U01.

In one subembodiment of the above embodiment, the second ID identifiesthe first node U01.

In one subembodiment of the above embodiment, a node indicated by thesecond ID is the first node U01.

In one embodiment, when the first node U01 forwards the first data blockset, a destination link layer ID list maintained by a node indicated bythe second ID does not comprise the first ID, and the first ID does notindicate a receiver of the first data block set.

In one subembodiment of the above embodiment, the first ID indicates thefirst node U01, and a receiver of the first data block set is a nodeother than the first node U01.

In one subembodiment of the embodiment, the second ID indicates a nodeother than the first node U01.

In one subembodiment of the embodiment, the second ID indicates areceiver of the first data block set.

In one embodiment, a receiver of the first data block set is a nodedrops forwarding the first data block set.

In one embodiment, the first node U01 has an IP address allocationfunction.

In one embodiment, when the first node U01 has an IP address allocationfunction, the first node U01 transmits the first message, and the firstmessage is used to configure an IP address of the 2a node U01.

In one subembodiment of the above embodiment, the IP address is IPv6 orIPv4.

In one subembodiment of the above embodiment, the first node U01allocates IP addresses to itself and the 2a node U02.

In one subembodiment of the above embodiment, an IP address of the firstnode U01 and an IP address of the 2a node U02 are at least the same inpartial bits.

In one subembodiment of the above embodiment, prefix fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, subnet fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, global ID fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, interface ID fields of anIP address of the first node U01 and an IP address of the 2a node U02are the same.

In one subembodiment of the above embodiment, global routing prefixfields of an IP address of the first node U01 and an IP address of the2a node U02 are the same.

In one subembodiment of the above embodiment, subnets of an IP addressof the first node U01 and an IP address of the 2a node U02 are the same.

In one subembodiment of the above embodiment, advantages of the abovemethod include, an IP address can indicate a plurality of nodes.

In one embodiment, when the first node U01 does not have an IP addressallocation function, the first node U01 receives the second message, andthe second message is used to indicate an IP address of the 2a node U02.

In one subembodiment of the above embodiment, the IP address is IPv6 orIPv4.

In one subembodiment of the above embodiment, the first node onlyallocates an IP address to itself.

In one subembodiment of the above embodiment, an IP address allocated tothe first node U01 itself and an IP address of the 2a node U02 are atleast the same in partial bits.

In one subembodiment of the above embodiment, subnets of an IP addressof the first node U01 and an IP address of the 2a node U02 are the same.

In one subembodiment of the above embodiment, prefix fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, subnet fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, global ID fields of an IPaddress of the first node U01 and an IP address of the 2a node U02 arethe same.

In one subembodiment of the above embodiment, interface ID fields of anIP address of the first node U01 and an IP address of the 2a node U02are the same.

In one subembodiment of the above embodiment, global routing prefixfields of an IP address of the first node U01 and an IP address of the2a node U02 are the same.

In one subembodiment of the above embodiment, advantages of the abovemethod include, an IP address can indicate a plurality of nodes.

In one embodiment, the 3a node U03 comprises a Proximity-services(Prose) Function.

In one embodiment, the 3a node U03 comprises a Mobility ManagementEntity (MME).

In one embodiment, the 3a node U03 comprises a Home Subscriber Server(HSS).

In one embodiment, the 3a node U03 comprises a Gateway (GW).

In one embodiment, the 3a node U03 comprises a server related to V2X.

In one embodiment, the 3a node U03 comprises an Application Function(AF).

In one embodiment, the 3a node U03 comprises a User Plane Function(UPF).

In one embodiment, the 3a node U03 comprises an Access and MobilityManagement Function (AMF).

In one embodiment, the 3a node U03 comprises a Session ManagementFunction (SMF).

In one embodiment, the 3a node U03 comprises a Network Exposure Function(NEF).

In one embodiment, the 3a node U03 comprises a Policy Control Function(PCF).

In one embodiment, the fourth message comprises at least one ID in thefirst ID set.

In one subembodiment of the above embodiment, the fourth messagecomprises the first ID.

In one subembodiment of the above embodiment, the fourth messagecomprises the second ID.

In one subembodiment of the above embodiment, a transmission of thefourth message is triggered by updating a layer 2 ID.

In one subembodiment of the above embodiment, a transmission of thefourth message is triggered by updating an application layer ID.

In one subembodiment of the above embodiment, a transmission of thefourth message is triggered by establishing a connection.

In one subembodiment of the above embodiment, a transmission of thefourth message is triggered by an IP address allocation or update.

In one subembodiment of the above embodiment, a transmission of thefourth message is triggered by establishing or updating a group.

In one subembodiment of the above embodiment, the fourth messageindicates a node identified by the first ID.

In one subembodiment of the above embodiment, the fourth messageindicates a node identified by the second ID.

In one embodiment, the third message is used to configure the firstcharging information, the third message is used to indicate a firstcollection period, the first data block set is operated within the firstcollection period, and the first charging information is generated forthe first collection period.

In one embodiment, the third message indicates a collection period, andthe first collection period is a collection period.

In one subembodiment of the embodiment, each collection period isorthogonal in time domain.

In one subembodiment of the embodiment, each collection period comprisesa start time and a duration time.

In one embodiment, the first node U01 generates charging information foreach collection period.

In one subembodiment of the embodiment, the first node U01 generates thefirst charging information for the first collection period.

In one embodiment, the first data block set is received in the firstcollection period.

In one embodiment, the third message indicates whether the firstcharging information is generated for transmission or reception.

In one embodiment, the third message indicates a type of an ID comprisedin the first charging information.

In one embodiment, the third message indicates a format or version ofthe first charging information.

In one embodiment, when the first charging information is generated, thefirst node immediately transmits the first charging information.

In one embodiment, after the first charging information is generated,the first node U01 transmits the first charging information in a timewindow.

In one subembodiment of the above embodiment, the time window isconfigured by the third message.

In one embodiment, the first feedback message is used to feed back thefirst charging information.

In one embodiment, the first charging feedback message indicatesreceived charging information.

In one embodiment, the first charging feedback message indicates acollection period corresponding to received charging information.

In one embodiment, the first charging feedback message indicates acollection period during which charging information is not received.

In one embodiment, the first charging feedback message indicates thatcharging information that is not received is used to trigger the firstnode U01 to retransmit charging information.

In one embodiment, the first message comprises a PC5-S message.

In one embodiment, the first message comprises a PC5-RRC message.

In one embodiment, the first message comprises an IP message.

In one embodiment, the fourth message and the third message are both NAXmessages.

In one embodiment, the first node U01 transmits a usage informationreport message, the usage information report message is an NAS message,and the usage information report message comprises the first charginginformation.

In one embodiment, the first charging feedback message is an NASmessage.

In one embodiment, the fifth message comprises a PC5-S message.

In one embodiment, the fifth message comprises a PC5-RRC message.

Embodiment 6

Embodiment 6 illustrates a flowchart of radio signal transmissionaccording to one embodiment of the present disclosure, as shown in FIG.6 . In FIG. 6 , the U11 corresponds to a first node in the presentdisclosure, the 3a node U12 is a node that is in communications with thefirst node U11, a 3b node U13 is a core network node. It is particularlyunderlined that the order illustrated in the embodiment does not putconstraints over sequences of signal transmissions and implementations.Embodiment 6 is based on Embodiment 5, and the parts needed but notshown in Embodiment 6 can be seen in Embodiment 5, where steps in F61are optional.

The first node U11 transmits a first data block set in step S6101;receives a second message in step S6102; and transmits first charginginformation in step S6103;

the 3a node U12 receives the first data block set in step S6201; andtransmits the second message in step S6202;

the 3b node U13 receives the first charging information in step S6301.

In Embodiment 6, a size of data in the first data block set is used togenerate the first charging information, the first charging informationcomprises a first ID set, and the first ID set comprises a first ID anda second ID; the first ID is a link layer ID; a source ID field of a MACheader of a MAC PDU used to carry the first data block set comprises atleast partial bits in a first ID, when a source link layer ID listmaintained by a node indicated by the second ID comprises the first ID,the first ID indicates a generator of the first data block set, and whena source link layer ID list maintained by a node indicated by the secondID does not comprise the first ID, the first ID does not indicate agenerator of the first data block set.

In one embodiment, the first node U11 is a UE.

In one embodiment, the 3a node U12 is a UE.

In one embodiment, the 3a node U12 is a remote UE.

In one embodiment, the first data block set is transmitted via a PC5interface.

In one embodiment, the first data block set is transmitted via asidelink.

In one embodiment, the first data block set occupies an STCH and anSCCH.

In one embodiment, a physical channel occupied by the first data blockset comprises a PSSCH.

In one embodiment, the first node U11 generates and transmits a MAC PDUset to carry the first data block set.

In one embodiment, the first data block set is transmitted within thefirst collection period.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set comprises at least partial bits in afirst ID.

In one subembodiment of the above embodiment, a source ID field of a MACheader of a MAC PDU used to carry the first data block set comprises 8most significant bits in a first ID.

In one subembodiment of the above embodiment, a source ID field of a MACheader of a MAC PDU used to carry the first data block set comprises 16most significant bits in a first ID.

In one embodiment, the first ID comprises 24 bits.

In one embodiment, the first data block set is forwarded by the firstnode U11.

In one embodiment, the first data block set is not forwarded by thefirst node U11.

In one subembodiment of the above embodiment, the action of not beingforwarded by the first node U11 includes, the first node U11 generatesthe first data block set.

In one subembodiment of the above embodiment, the action of not beingforwarded by the first node U11 includes, the first data block set isgenerated by a higher layer of the first node.

In one subembodiment of the above embodiment, when using layer 2forwarding or relaying, the action of not being forwarded by the firstnode U11 includes, the first data block set is generated by a layerabove the layer 2 of the first node U11.

In one subembodiment of the above embodiment, when using layer 3forwarding or relaying, the action of not being forwarded by the firstnode U11 includes, the first data block set is generated by anapplication layer of the first node U11.

In one embodiment, the forwarding action includes relaying.

In one embodiment, an SRC field of a MAC PDU header carrying the firstdata block set identifies the first node U11; a DST field of a MAC PDUheader carrying the first data block set is used to identify the 3a nodeU12.

In one embodiment, when the first data block set is not forwarded by thefirst node U11, a source link layer ID list maintained by a nodeindicated by the second ID comprises the first ID, and the first IDidentifies a generator of the first data block set.

In one subembodiment of the above embodiment, the first ID identifiesthe first node U11.

In one subembodiment of the above embodiment, the second ID identifiesthe first node U11.

In one subembodiment of the above embodiment, a node indicated by thesecond ID is the first node U11.

In one embodiment, when the first node U11 forwards the first data blockset, a source link layer ID list maintained by a node indicated by thesecond ID does not comprise the first ID, and the first ID does notindicate a generator of the first data block set.

In one subembodiment of the above embodiment, the first ID indicates thefirst node U11, and a generator of the first data block set is a nodeother than the first node U11.

In one subembodiment of the embodiment, the second ID indicates a nodeother than the first node U11.

In one subembodiment of the embodiment, the second ID indicates agenerator of the first data block set.

In one embodiment, a generator of the first data block set is a nodegenerating the first data block set.

In one embodiment, the first node U11 does not have an IP addressallocation function, the first node U11 receives the second message, andthe second message is used to indicate an IP address of the 3a node U12.

In one subembodiment of the above embodiment, the IP address is IPv6 orIPv4.

In one subembodiment of the above embodiment, the first node onlyallocates an IP address to itself.

In one subembodiment of the above embodiment, an IP address allocated tothe first node U11 itself and an IP address of the 3a node U12 are atleast the same in partial bits.

In one subembodiment of the above embodiment, subnets of an IP addressof the first node U11 and an IP address of the 3a node U12 are the same.

In one subembodiment of the above embodiment, prefix fields of an IPaddress of the first node U11 and an IP address of the 3a node U12 arethe same.

In one subembodiment of the above embodiment, subnet fields of an IPaddress of the first node U11 and an IP address of the 3a node U12 arethe same.

In one subembodiment of the above embodiment, global ID fields of an IPaddress of the first node U11 and an IP address of the 3a node U12 arethe same.

In one subembodiment of the above embodiment, interface ID fields of anIP address of the first node U11 and an IP address of the 3a node U12are the same.

In one subembodiment of the above embodiment, global routing prefixfields of an IP address of the first node U11 and an IP address of the3a node U12 are the same.

In one subembodiment of the above embodiment, advantages of the abovemethod include, an IP address can indicate a plurality of nodes.

In one embodiment, the 3b node U13 comprises a Prose Function.

In one embodiment, the 3b node U13 includes MME.

In one embodiment, the 3b node U13 comprises an HSS.

In one embodiment, the 3b node U13 comprises a GW.

In one embodiment, the 3b node U13 comprises a server related to V2X.

In one embodiment, the 3b node U13 comprises an AF.

In one embodiment, the 3b node U13 comprises a UPF.

In one embodiment, the 3b node U13 comprises an AMF.

In one embodiment, the 3b node U13 comprises an SMF.

In one embodiment, the 3b node U13 comprises an NEF.

In one embodiment, the 3b node U13 comprises a PCF.

In one embodiment, the first charging information is used for generatinga charging report.

Embodiment 7

Embodiment 7 illustrates a flowchart of radio signal transmissionaccording to one embodiment of the present disclosure, as shown in FIG.7 . In FIG. 7 , the U21 corresponds to a first node in the presentdisclosure, a 2c node U22 is a node in communications with the firstnode U21, a 2d node U23 is a node in communications with the first nodeU21. It is particularly underlined that the order illustrated in theembodiment does not put constraints over sequences of signaltransmissions and implementations. Embodiment 7 is based on Embodiment 5and Embodiment 6, and the parts needed but not shown in Embodiment 7 canbe seen in Embodiment 5 and Embodiment 6.

The first node U21 receives a first MAC PDU set in step S7101; transmitsa first data block set in step S7102; and transmits first charginginformation in step S7103;

the 2c node U22 receives the first data block set in step S7201;

the 2d node U23 transmits the first MAC PDU set in step S7301.

In Embodiment 7, a size of data in the first data block set is used togenerate the first charging information, the first charging informationcomprises a first ID set, and the first ID set comprises a first ID anda second ID; the first ID is a link layer ID; when a source link layerID list maintained by a node indicated by the second ID comprises thefirst ID, the first ID indicates a generator of the first data blockset, and when a source link layer ID list maintained by a node indicatedby the second ID does not comprise the first ID, the first ID does notindicate a generator of the first data block set.

In one embodiment, the first MAC PDU set at least comprises one MAC PDU.

In one embodiment, the first MAC PDU set is transmitted via a PC5interface.

In one embodiment, the first MAC PDU set is transmitted via a Uuinterface.

In one embodiment, a physical channel occupied by the first MAC PDU setcomprises a PSSCH.

In one embodiment, a logical channel occupied by the first MAC PDU setcomprises an SCCH.

In one embodiment, a logical channel occupied by the first MAC PDU setcomprises an STCH.

In one embodiment, a physical channel occupied by the first MAC PDU setcomprises a PDSCH.

In one embodiment, a physical channel occupied by the first MAC PDU setcomprises a PUSCH.

In one embodiment, the first MAC PDU set bears the first data block set.

In one embodiment, the first MAC PDU set carries the first data blockset.

In one embodiment, the first MAC PDU set is transmitted within the firstcollection period.

In one embodiment, a MAC SDU of a MAC PDU in the first MAC PDU setcarries the first data block set.

In one embodiment, a generator of the first data block set is the 2dnode U23.

In one embodiment, the first charging information is generated for datatransmission.

In one embodiment, the first charging information is generated for dataof the first data block set being transmitted.

In one embodiment, the first charging information is generated for thefirst data block set being forwarded or relayed.

In one embodiment, the first data block set is encapsulated in a MAC PDUset and forwarded to the 2c node U22.

In one embodiment, a source ID field of a MAC header of a MAC PDU usedto carry the first data block set is an SRC field.

In one embodiment, the first ID is an ID of the first node U21.

In one embodiment, the first ID indicates the first node U21.

In one embodiment, the second ID is used to indicate the 2d node U23.

In one embodiment, the second ID is an IP address, and the firstcharging information does not comprise an IP address of the first nodeU21.

In one embodiment, the second ID is an application layer ID, and thefirst charging information does not comprise an application layer ID ofthe first node U21.

In one embodiment, the first charging information comprises two sourceidentities, one of which is the first ID, and the other is the secondID.

In one embodiment, the MAC PDU carrying the first data block set is aMAC PDU in the first MAC PDU set, and the first ID is used to indicatethe 2d node U23.

In one subembodiment of the above embodiment, the second ID is used toindicate the 2d node U23.

In one subembodiment of the above embodiment, the 2d node U23 is agenerator of the first data block.

In one subembodiment of the above embodiment, a source link layer IDmaintained by a node indicated by the second ID comprises the first ID.

In one subembodiment of the above embodiment, the second ID indicatesthe 2d node U23.

In one subembodiment of the above embodiment, the first charginginformation comprises an ID used to indicate the 2c node U22.

In one embodiment, the first ID indicates the first node U21, the secondID indicates the 2d node U23, the first charging information comprises athird ID, and the third ID indicates the 2c node U22.

Embodiment 8

Embodiment 8 illustrates a flowchart of radio signal transmissionaccording to one embodiment in the present disclosure, as shown in FIG.8 . In FIG. 8 , the U31 corresponds to a first node in the presentdisclosure, a 2e node U32 is a node in communications with the firstnode U31, a 2f node U33 is a node in communications with the first nodeU31. It is particularly underlined that the order illustrated in theembodiment does not put constraints over sequences of signaltransmissions and implementations. Embodiment 8 is based on Embodiment 5and Embodiment 6, and the parts needed but not shown in Embodiment 8 canbe seen in Embodiment 5 and Embodiment 6.

The first node U31 receives a first data block set in step S8101;transmits a second MAC PDU in step S8102; and transmits first charginginformation in step S8103;

the 2e node U32 receives the second MAC PDU set in step S8201;

the 2f node U33 transmits the first data block set in step S8301.

In Embodiment 8, a size of data in the first data block set is used togenerate the first charging information, the first charging informationcomprises a first ID set, and the first ID set comprises a first ID anda second ID; the first ID is a link layer ID; a destination ID field ofa MAC header of a MAC PDU used to carry the first data block setcomprises at least partial bits in a first ID, when a destination linklayer ID list maintained by a node indicated by the second ID comprisesthe first ID, the first ID identifies a receiver of the first data blockset, and when a destination link layer ID list maintained by a nodeindicated by the second ID does not comprise the first ID, the first IDdoes not indicate a receiver of the first data block set.

In one embodiment, the second MAC PDU set at least comprises one MACPDU.

In one embodiment, the second MAC PDU set is transmitted via a PC5interface.

In one embodiment, the second MAC PDU set is transmitted via a Uuinterface.

In one embodiment, a physical channel occupied by the second MAC PDU setcomprises a PSSCH.

In one embodiment, a logical channel occupied by the second MAC PDU setcomprises an SCCH.

In one embodiment, a logical channel occupied by the second MAC PDU setcomprises an STCH.

In one embodiment, a physical channel occupied by the second MAC PDU setcomprises a PDSCH.

In one embodiment, a physical channel occupied by the second MAC PDU setcomprises a PUSCH.

In one embodiment, the second MAC PDU set bears the first data blockset.

In one embodiment, the second MAC PDU set carries the first data blockset.

In one embodiment, the second MAC PDU set is transmitted within thefirst collection period.

In one embodiment, a MAC SDU of a MAC PDU in the second MAC PDU setcarries the first data block set.

In one embodiment, a generator of the first data block set is the 2fnode U33.

In one embodiment, the first charging information is generated for databeing received.

In one embodiment, the first charging information is generated for dataof the first data block set being received.

In one embodiment, the first charging information is generated for thefirst data block set being forwarded or relayed.

In one embodiment, the first data block set is encapsulated in thesecond MAC PDU set and forwarded to the 2e node U32.

In one embodiment, a destination ID field of a MAC header of a MAC PDUused to carry the first data block set is a DST field.

In one embodiment, the first ID is an ID of the first node U31.

In one embodiment, the first ID indicates the first node U31.

In one embodiment, the second ID is used to indicate the 2e node U32.

In one embodiment, the second ID is an IP address, and the firstcharging information does not comprise an IP address of the first nodeU31.

In one embodiment, the second ID is an application layer ID, and thefirst charging information does not comprise an application layer ID ofthe first node U31.

In one embodiment, the first charging information comprises twodestination identities, one of which is the first ID, and the other isthe second ID.

In one embodiment, the MAC PDU carrying the first data block set is aMAC PDU in the second MAC PDU set, and the first ID is used to indicatethe 2e node U32.

In one subembodiment of the above embodiment, the second ID is used toindicate the 2e node U32.

In one subembodiment of the above embodiment, the first charginginformation comprises an ID used to indicate the 2f node U33.

In one embodiment, the first ID indicates the first node U31, the secondID indicates the 2e node U32, the first charging information comprises afourth ID, and the fourth ID indicates the 2f node U33.

Embodiment 9

Embodiment 9 illustrates a schematic diagram of a MAC PDU according toone aspect of the present disclosure, as shown in FIG. 9 .

In Embodiment 9, a MAC PDU comprises a MAC header and at least one MACsubPDU; and the MAC header comprises a source ID, a destination ID andother bits.

In one embodiment, the MAC PDU is transmitted on a SideLink SharedCHannel (SL-SCH).

In one embodiment, a number of bits comprised in the MAC header isfixed.

In one embodiment, a number of bits comprised in the MAC header is 32.

In one embodiment, the MAC header is an SL-SCH MAC subheader.

In one embodiment, the MAC header is an SL-SCH subheader.

In one embodiment, the other bits comprise 5 fields, V, R, R, R, and R,and numbers of bits comprised are 4, 1, 1, 1 and 1 respectively.

In one embodiment, the source ID and the destination ID respectivelycomprise 16 bits and 8 bits.

In one embodiment, the source ID in the MAC header and the destinationID in the MAC header are respectively an SRC field and a DST field.

In one embodiment, each MAC subPDU comprises a MAC subheader and a MACSDU, a MAC subheader in each MAC subPDU comprises a Logical ChannelIDentifier (LCID) field, and the LCID field indicates a channel ID of alogical channel corresponding to a MAC SDU.

In one embodiment, the LCID field comprises 5 bits.

In one embodiment, the LCID field comprises 6 bits.

In one embodiment, each MAC PDU is also allowed to comprise a paddingbit.

In one embodiment, a MAC subPDU comprises an RLC PDU.

In one embodiment, a MAC subPDU comprises a MAC CE.

In one embodiment, the MAC PDU in FIG. 9 carries the first data blockset.

In one embodiment, the MAC PDU in FIG. 9 is a MAC PDU in a first MAC PDUset in Embodiment 1 in the present disclosure.

In one embodiment, the MAC PDU in FIG. 9 is a MAC PDU in a second MACPDU set in Embodiment 1 in the present disclosure.

In one embodiment, the MAC PDU in FIG. 9 is a MAC PDU in a first MAC PDUset in Embodiment 7 in the present disclosure.

In one embodiment, the MAC PDU in FIG. 9 is a MAC PDU in a second MACPDU set in Embodiment 8 in the present disclosure.

Embodiment 10

Embodiment 10 illustrates a schematic diagram of a link layer ID listmaintained by a node indicated by a second ID according to oneembodiment of the present disclosure, as shown in FIG. 10 .

In one embodiment, the link layer ID list maintained by a node indicatedby the second ID is a source ID list.

In one embodiment, the link layer ID list maintained by a node indicatedby the second ID is a destination ID list.

In one embodiment, the link layer ID list maintained by a node indicatedby the second ID illustrated in FIG. 10 comprises I link layer ID(s), Ibeing a positive integer.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes a destinationlink layer ID list of a node indicated by the second ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes a destinationlink layer ID list owned by a node indicated by the second ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that the IDlist is a data structure comprising at least one ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that the IDlist is a table comprising at least one ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that the IDlist is a list comprising at least one ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that the IDlist is a set comprising at least one ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that the IDlist is a group comprising at least one ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes alldestination link layer IDs of a node indicated by the second ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes a destinationlink layer ID of a node indicated by the second ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes alldestination link layer IDs of a node indicated by the second ID.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that when adestination ID indicated by a received DST field of a MAC PDU headerbelongs to the destination link layer ID list, the MAC PDU is processed.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that when adestination ID indicated by a received DST field of a MAC PDU headerbelongs to the destination link layer ID list, the MAC PDU is forwardedor handed over to a higher layer for processing.

In one embodiment, the phrase of “a destination link layer ID listmaintained by a node indicated by the second ID” includes that when adestination ID indicated by a received DST field of a MAC PDU headerdoes not belong to the destination link layer ID list, the MAC PDU isdropped.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes a source link layer IDlist of a node indicated by the second ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes a source link layer IDlist owned by a node indicated by the second ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that the ID list is adata structure comprising at least one ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that the ID list is atable comprising at least one ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that the ID list is alist comprising at least one ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that the ID list is a setcomprising at least one ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that the ID list is agroup comprising at least one ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes all source link layer IDsof a node indicated by the second ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes at least one source linklayer ID of a node indicated by the second ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes a source link layer ID ofa node indicated by the second ID.

In one embodiment, the phrase of “a source link layer ID list maintainedby a node indicated by the second ID” includes that a source IDindicated by an SRC field of a MAC PDU header received by a relay nodeis used to indicate a generator of the MAC PDU.

Embodiment 11

Embodiment 11 illustrates a schematic diagram of a collection periodaccording to one embodiment of the present disclosure, as shown in FIG.11 .

In one embodiment, the third message indicates a collection period.

In one embodiment, a time length of each collection period is the same.

In one embodiment, the first collection period is one of all collectionperiods.

In one embodiment, the third message indicates a time length of acollection period.

In one embodiment, the collection period is measured by s.

In one embodiment, the collection period is measured by ms.

In one embodiment, the collection period is measured by subframe.

In one embodiment, the collection period is measured by superframe.

In one embodiment, the third message is used to indicate a start timeand an end time of a collection period.

In one embodiment, the third message explicitly indicates a time lengthof the collection period; the third message does not indicate a starttime of the collection period, and a receiver of the third messagedetermines a start time of the collection period.

In one embodiment, the first node counts a size of data operated withinthe first collection period.

Embodiment 12

Embodiment 12 illustrates a schematic diagram of a size of data in afirst data block set being used to generate first charging informationaccording to one embodiment of the present disclosure, as shown in FIG.12 .

In one embodiment, the first node receives a third message, and thethird message is used to configure the first charging information.

In one embodiment, the third message is used to indicate the firstcollection period.

In one embodiment, the first data block set is operated within the firstcollection period.

In one embodiment, when the operating action is receiving, a size ofdata in the first data block set is used to generate the first charginginformation for receiving.

In one embodiment, when the operating action is transmitting, a size ofdata in the first data block set is used to generate the first charginginformation for transmitting.

In one embodiment, a size of data of the first data block set comprisesa number of data blocks.

In one embodiment, a size of data of the first data block set comprisesa number of bits of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of Mbits of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of Gbits of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of Tbits of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of Bytes of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of MBs of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of GBs of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of TBs of a data block.

In one embodiment, a size of data of the first data block set comprisesa number of resources occupied by a data block.

In one embodiment, a number of the first data block sets comprises anumber of IP packets and a number of non-IP packets.

In one embodiment, the first data block set comprises P data block(s),and a number P of the P data block(s) is recorded by the first charginginformation.

In one embodiment, the first data block set comprises KN bit(s), whereKN is a positive integer, and KN is recorded by the first charginginformation.

In one embodiment, the first data block set comprises KN bit(s), whereKN is a positive integer, and a quantized value of KN is recorded by thefirst charging information.

In one subembodiment of the above embodiment, the third messageconfigures the quantization.

In one embodiment, the first data block set comprises KN bit(s), whereKN is a positive integer, and a larger one between KN and a fixed numberis recorded by the first charging information.

In one embodiment, the first data block set comprises KN bit(s), whereKN is a positive integer, and a smaller one between KN and a fixednumber is recorded by the first charging information.

In one embodiment, the first charging information comprises a value of aproduct of a size of data in the first data block set and a fixednumber.

In one embodiment, the fixed number comprises a real number.

In one embodiment, the fixed number/static value is configured by thethird message.

In one embodiment, a size of data of the first data block set and afirst collection period are used together to determine an average datarate, and the first charging information comprises the average datarate.

In one embodiment, a result obtained after a size of data of the firstdata block set is processed by a filter is comprised in the firstcharging information, where the filter is configured by the network.

Embodiment 13

Embodiment 13 illustrates a schematic diagram of a fifth message beingused to synchronize collection periods of different nodes according toone embodiment of the present disclosure, as shown in FIG. 13 .

In one embodiment, the fifth message is used to synchronize the firstcollection period and a second collection period, the first nodereceives the first data block set, and a transmitter of the first datablock set generates charging information for the second collectionperiod.

In one subembodiment of the above embodiment, the first collectionperiod is a current collection period of the first node.

In one subembodiment of the above embodiment, the second collectionperiod is a current collection period of a transmitter of the first datablock set.

In one embodiment, the fifth message is used to synchronize the firstcollection period and a third collection period, the first nodetransmits the first data block set, and a receiver of the first datablock set generates charging information for the third collectionperiod.

In one subembodiment of the above embodiment, the first collectionperiod is a current collection period of the first node.

In one subembodiment of the above embodiment, the third collectionperiod is a current collection period of a receiver of the first datablock set.

In one embodiment, the fifth message is a PC5-S message.

In one embodiment, the fifth message is an application layer message.

In one embodiment, the fifth message is a NAS message.

In one embodiment, the fifth message is transmitted via a PC5 interface.

In one embodiment, the fifth message is transmitted via a sidelink.

In one embodiment, the fifth message indicates a start time of the firstcollection period.

In one embodiment, the fifth message indicates a period of the firstcollection period.

In one embodiment, the fifth message indicates a time length of thefirst collection period.

In one embodiment, the fifth message indicates a reference time.

In one embodiment, the first charging information comprises timeinformation of a current collection period.

In one subembodiment of the above embodiment, the time informationcomprises a timestamp.

In one embodiment, advantages of the above embodiment includes,different nodes can synchronize their own collection periods to reducecomplexity of the core network to check charging information ofdifferent nodes, meanwhile, due to synchronization and other reasons,the adjustment of a collection period results in hopping in a length ofa period, and first charging information can indicate a length of thecollection period.

Embodiment 14

Embodiment 14 illustrates a structure block diagram of a processingdevice in a first node according to one embodiment of the presentdisclosure; as shown in FIG. 14 . In FIG. 14 , a processing device 1400in a first node comprises a first receiver 1401 and a first transmitter1402. In Embodiment 14,

the first receiver 1401 operates a first data block set; and

the first transmitter 1402 transmits first charging information;

herein, a size of data in the first data block set is used to generatethe first charging information, the first charging information comprisesa first ID set, and the first ID set comprises a first ID and a secondID; the first ID is a link layer ID; the operating action is receiving,a destination ID field of a MAC header of a MAC PDU used to carry thefirst data block set comprises at least partial bits in a first ID, whena destination link layer ID list maintained by a node indicated by thesecond ID comprises the first ID, the first ID identifies a receiver ofthe first data block set, and when a destination link layer ID listmaintained by a node indicated by the second ID does not comprise thefirst ID, the first ID does not indicate a receiver of the first datablock set; or, the operating action is transmitting, a source ID fieldof a MAC header of a MAC PDU used to carry the first data block setcomprises at least partial bits in a first ID, when a source link layerID list maintained by a node indicated by the second ID comprises thefirst ID, the first ID indicates a generator of the first data blockset, and when a source link layer ID list maintained by a node indicatedby the second ID does not comprise the first ID, the first ID does notindicate a generator of the first data block set.

In one embodiment, when the operating action is receiving, the firstcharging information is generated for data reception; and when theoperating action is transmitting, the first charging information isgenerated for data transmission.

In one embodiment, the first charging information comprises firstinformation, when the first charging information is generated for datareception, the first information is used to indicate whether the firstID identifies a receiver of the first data block set; when the firstcharging information is generated for data transmission, the firstinformation is used to indicate whether the first ID identifies agenerator of the first data block set.

In one embodiment, when the operating action is receiving and the firstID does not indicate a receiver of the first data block set, the secondID is used to indicate a receiver of the first data block set; when theoperating action is transmitting and the first ID does not indicate agenerator of the first data block set, the second ID is used to indicatea generator of the first data block set.

In one embodiment, when the operating action is receiving, the second IDis an IP address of a receiver of the first data block set; when theoperating action is transmitting, the second ID is an IP address of agenerator of the first data block set.

In one embodiment, the second ID is a first application layer ID, andthe first application layer ID is an ID related to an application layer.

In one embodiment, the second ID is a first group ID, the first group IDidentifies a first group, and the first group comprises a receiver of afirst data block set and a generator of the first data block set.

In one embodiment, the second ID is a link layer ID.

In one embodiment, the second ID is a flow ID.

In one embodiment, when the operating action is receiving, and the firstID does not indicate a receiver of the first data block set, or, whenthe operating action is transmitting, and the first ID does not indicatea generator of the first data block set, the first charging informationonly comprises an IP address other than an IP address of the first node.

In one embodiment, when the operating action is receiving, and the firstID does not indicate a receiver of the first data block set, or, whenthe operating action is transmitting, and the first ID does not indicatea generator of the first data block set, the first charging informationonly comprises an application layer ID other than an application layerID of the first node.

In one embodiment, when the operating action is receiving, and the firstID does not indicate a receiver of the first data block set, or, whenthe operating action is transmitting, and the first ID does not indicatea generator of the first data block set, the first charging informationonly comprises a link layer ID other than a link layer ID of the firstnode.

In one embodiment, when the first node has an IP address allocationfunction, the first transmitter 1402 transmits first message, and thefirst message configures an IP address of a transmitter of the firstdata block set; when the first node does not have an IP addressallocation function, the first receiver 1401 receives a second message,and the second message indicates an IP address of a transmitter of thefirst data block set.

In one embodiment, an IP address of the first node and an IP address ofa transmitter of the first data block set are at least the same inpartial bits.

In one embodiment, the first transmitter 1402, transmits a fourthmessage, and the fourth message comprises at least one ID in the firstID set.

In one embodiment, the first receiver 1401 receives a third message, thethird message is used to configure the first charging information, thethird message is used to indicate a first collection period, the firstdata block set is operated within the first collection period, and thefirst transmitter 1402 generates the first charging information for thefirst collection period.

In one embodiment, the first receiver 1401, receives a first chargingfeedback message, and the first charging feedback message indicatesreceived charging information.

In one embodiment, the first transmitter 1402, transmits a fifthmessage, and the fifth message is used to synchronize collection periodsof different nodes.

In one embodiment, the first node is a UE.

In one embodiment, the first node is a terminal that supports large timedelay differences.

In one embodiment, the first node is a terminal that supports NTN.

In one embodiment, the first node is an aircraft.

In one embodiment, the first node is a vehicle terminal.

In one embodiment, the first node is a relay.

In one embodiment, the first node is a vessel.

In one embodiment, the first node is a IoT terminal.

In one embodiment, the first node is a IIoT terminal.

In one embodiment, the first node is a device that supports transmissionwith low-latency and high-reliability.

In one embodiment, the first receiver 1401 comprises at least one of theantenna 452, the receiver 454, the receiving processor 456, themulti-antenna receiving processor 458, the controller/processor 459, thememory 460 or the data source 467 in Embodiment 4.

In one embodiment, the first transmitter 1402 comprises at least one ofthe antenna 452, the transmitter 454, the transmitting processor 468,the multi-antenna transmitting processor 457, the controller/processor459, the memory 460 or the data source 467 in Embodiment 4.

The ordinary skill in the art may understand that all or part of stepsin the above method may be implemented by instructing related hardwarethrough a program. The program may be stored in a computer readablestorage medium, for example Read-Only Memory (ROM), hard disk or compactdisc, etc. Optionally, all or part of steps in the above embodimentsalso may be implemented by one or more integrated circuits.Correspondingly, each module unit in the above embodiment may berealized in the form of hardware, or in the form of software functionmodules. The present disclosure is not limited to any combination ofhardware and software in specific forms. The UE and terminal in thepresent disclosure include but not limited to unmanned aerial vehicles,communication modules on unmanned aerial vehicles, telecontrolledaircrafts, aircrafts, diminutive airplanes, mobile phones, tabletcomputers, notebooks, vehicle-mounted communication equipment, wirelesssensor, network cards, terminals for Internet of Things, RFID terminals,NB-IOT terminals, Machine Type Communication (MTC) terminals, enhancedMTC (eMTC) terminals, data cards, low-cost mobile phones, low-costtablet computers, satellite communication equipment, vesselcommunication equipment, NTN UEs, etc. The base station or system devicein the present disclosure includes but is not limited to macro-cellularbase stations, micro-cellular base stations, home base stations, relaybase station, gNB (NR node B), Transmitter Receiver Point (TRP), NTNbase stations, satellite equipment, flight platform equipment and otherradio communication equipment.

The above are merely the preferred embodiments of the present disclosureand are not intended to limit the scope of protection of the presentdisclosure. Any modification, equivalent substitute and improvement madewithin the spirit and principle of the present disclosure are intendedto be included within the scope of protection of the present disclosure.

What is claimed is:
 1. A first node for wireless communications,comprising: a first receiver, operating a first data block set; and afirst transmitter, transmitting first charging information; wherein asize of data in the first data block set is used to generate the firstcharging information, the first charging information comprises a firstidentity (ID) set, and the first ID set comprises a first ID and asecond ID; the first ID is a link layer ID; the operating action isreceiving, a destination ID field of a MAC header of a MAC PDU used tocarry the first data block set comprises at least partial bits in thefirst ID, when a destination link layer ID list maintained by a nodeindicated by the second ID comprises the first ID, the first IDidentifies a receiver of the first data block set, and when adestination link layer ID list maintained by a node indicated by thesecond ID does not comprise the first ID, the first ID does not indicatea receiver of the first data block set.
 2. The first node according toclaim 1, wherein when the operating action is receiving, the firstcharging information is generated for data reception; the first charginginformation comprises first information, when the first charginginformation is generated for data reception, the first information isused to indicate whether the first ID identifies a receiver of the firstdata block set.
 3. The first node according to claim 1, wherein when theoperating action is receiving, the first charging information isgenerated for data reception; when the operating action is receiving andthe first ID does not indicate a receiver of the first data block set,the second ID is used to indicate a receiver of the first data blockset.
 4. The first node according to claim 3, wherein the second ID is afirst group ID, the first group ID identifies a first group, and thefirst group comprises a receiver of the first data block set and agenerator of the first data block set.
 5. The first node according toclaim 1, wherein when the operating action is receiving, the firstcharging information is generated for data reception when the operatingaction is receiving, and the first ID does not indicate a receiver ofthe first data block set, the first charging information only comprisesan IP address other than an IP address of the first node.
 6. The firstnode according to claim 5, wherein an IP address of the first node andan IP address of a transmitter of the first data block set are at leastthe same in partial bits.
 7. The first node according to claim 6,wherein the second ID is a link layer ID.
 8. The first node according toclaim 1, wherein when the operating action is receiving, the firstcharging information is generated for data reception; when the operatingaction is receiving and the first ID does not indicate a receiver of thefirst data block set, the first charging information only comprises anapplication layer ID other than an application layer ID of the firstnode.
 9. The first node according to claim 1, wherein when the operatingaction is receiving, the first charging information is generated fordata reception; when the operating action is receiving and the first IDdoes not indicate a receiver of the first data block set, the firstcharging information only comprises a link layer ID other than a linklayer ID of the first node.
 10. The first node according to claim 1,wherein when the first node has an IP address allocation function, thefirst transmitter transmits first information, and the first messageconfigures an IP address of a transmitter of the first data block set;when the first node does not have an IP address allocation function, thefirst receiver receives a second message, and the second messageindicates an IP address of a transmitter of the first data block set.11. The first node according to claim 1, wherein when the operatingaction is receiving and the first data block set is data that needs tobe relayed, the first ID is used to indicate the first node, a receiverof the first data block set is a receiver of the first data after beingrelayed, the receiver of the first data block set is a node other thanthe first node, and the second ID is used to indicate a receiver of thefirst data block set; the first information indicates data when thefirst data block set needs to be relayed.
 12. The first node accordingto claim 11, wherein the first charging information comprises two sourceIDs, one of which is the first ID, and the other is the second ID. 13.The first node according to claim 12, wherein the second ID is a firstgroup ID, the first group ID identifies a first group, and the firstgroup comprises a receiver of the first data block set and a generatorof the first data block set.
 14. The first node according to claim 1,comprising: the first receiver, receiving a third message, the thirdmessage being used to configure the first charging information, thethird message being used to indicate a first collection period, thefirst data block set being operated within the first collection period,and the first transmitter, generating the first charging information forthe first collection period; the first transmitter, transmitting a fifthmessage, the fifth message being used to synchronize collection periodsof different nodes.
 15. The first node according to claim 14, whereinthe third message explicitly indicates a time length of the collectionperiod; the third message does not indicate a start time of thecollection period, and a receiver of the third message determines astart time of the collection period.
 16. The first node according toclaim 15, wherein the first receiver receives a first charging feedbackmessage, the first charging feedback message indicates received charginginformation; the first charging feedback message indicates a collectionperiod during which charging information is not received; the firstcharging feedback message indicates that charging information not beingreceived is used to trigger the first node to retransmit charginginformation.
 17. The first node according to claim 14, wherein a resultobtain after a size of data of the first data block set is processed bya filter is comprised in the first charging information, where thefilter is configured by the network.
 18. The first node according toclaim 14, wherein the first charging information comprises a value of aproduct of the size of data in the first data block set and a fixednumber.
 19. The first node according to claim 14, wherein when theoperating action is receiving, and the first data block set is data thatneeds to be relayed, the first ID is used to indicate the first node, areceiver of the first data block set is a receiver of the first dataafter being relayed, the receiver of the first data block set is a nodeother than the first node, and the second ID is used to indicate areceiver of the first data block set; the first information indicatesdata when the first data block set needs to be relayed.
 20. A method ina first node for wireless communications, comprising: operating a firstdata block set; and transmitting first charging information; wherein asize of data in the first data block set is used to generate the firstcharging information, the first charging information comprises a firstID set, and the first ID set comprises a first ID and a second ID; thefirst ID is a link layer ID; the operating action is receiving, adestination ID field of a MAC header of a MAC PDU used to carry thefirst data block set comprises at least partial bits in a first ID, whena destination link layer ID list maintained by a node indicated by thesecond ID comprises the first ID, the first ID identifies a receiver ofthe first data block set, and when a destination link layer ID listmaintained by a node indicated by the second ID does not comprise thefirst ID, the first ID does not indicate a receiver of the first datablock set.